-
Notifications
You must be signed in to change notification settings - Fork 336
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
T6773: RFC-2136 support for Kea DHCP4 server #4153
base: current
Are you sure you want to change the base?
Conversation
👍 |
✅ No issues found in unused-imports check.. Please refer the workflow run |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The idea is good, I left some ideas for improvements in the review.
Did a few cosmetic things. Please let me know what you think about generating that config, DNS servers list and the port 53001 for d2 and I'll get it fixed within a few days. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems to be an issue in the XML definition stopping the CI tests. I will try find time later to pinpoint the failing syntax.
Was able to figure it out. Should be fine now. |
… into feature/dhcpv4-ddns
899b0a4
to
8b6d4ae
Compare
Everything seems to be fixed now, all tests are green |
…uage due to how Kea treats set/unset options in scopes
So I started productionising this setup, which meant setting up more sophisticated configurations for DHCP. And I quickly realised that this config language wasn't doing what was actually needed. The main problem is that in Kea it makes a difference if an attribute is set to false or not set at all. It's to do with how the DDNS settings cascade to nested scopes. Let's say you set I've re-implemented the behavioral settings in a way that they can be explicitly set to enabled or disabled, or left out/deleted from config, the latter will result in a removal of the attribute from the output config file. This way I got the whole thing to function properly, even though the language has become a bit more heavyweight. If you have any ideas about how to make it nicer and easier to understand for the end user, I'm open to suggestions. |
CI integration 👍 passed! Details
|
Change Summary
This PR introduces support for RFC-2136 DDNS updates in Kea DHCP4 server.
Types of changes
Related Task(s)
https://vyos.dev/T6773
Related PR(s)
vyos/vyos-documentation#1561
Component(s) name
dhcp-server
Proposed changes
Introduces new configuration parameters under service dhcp-server and the logic to translate it into Kea 2.4.1 configuration language.
How to test
Set up a Technitium DNS in a container inside VyOS. Set up DDNS updates as follows:
Get the DHCP server to issue some leases and check if the DNS server gets updated.
Smoketest result
Checklist: